Incorporate workflow_run into the CI so that triggered workflows are easier restarted #789
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ra", and "trivyscan" workflows. Expecting this to allow quicker re-runs of failed workflows where we currently have to wait until the CI has finished before we can re-run a failure.
maxstack
force-pushed
the
ci/workload_run
branch
7 times, most recently
from
fd80c26 to
adf3b62
Compare
…n only trigger on the workflow name
maxstack
force-pushed
the
ci/workload_run
branch
from
adf3b62 to
e2dfc7e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We don't want to have to wait until the complete CI workflow has finished before we can re-run any failed parts.
The workflow_run trigger slightly decouples the
stackhpc,extra, andtrivyscanworkflows from themainCI workflow in a way that makes them easier to restart whilstmainis still running.